Skip to content

feat(aws-agents): update skills to reflect AgentCore CLI v1 - #522

Merged
notgitika merged 10 commits into
gitika/agentcore-cli-v1from
nickdb/agentcore-cli-v1
Oct 29, 2026
Merged

notgitika merged 10 commits into
gitika/agentcore-cli-v1from
nickdb/agentcore-cli-v1

Conversation

@nborges-aws

Copy link
Copy Markdown

Description

Updates AgentCore skills for AgentCore CLI v1.0.0, complementing the skills covered by PR #502. The changes in this PR replace v0 commands and project shapes, correct v1 workflow guidance, and fix issues found during multiple review rounds.

Skills and files covered

  • agents-build:
    • v1 Runtime and Harness configuration, project migration, VPC setup, and resource removal
    • deployment targets, Runtime invocation, session history, shared Memory, and multi-agent IAM
    • request header forwarding using the Python SDK’s context.request_headers
    • Payments setup and integration examples, including operator-created instruments and sessions
  • agents-connect:
    • v1 Gateway targets, connectors, credentials, and Cedar policy commands
    • Gateway URL lookup from the deployed Gateway ID
    • target selection carried through deploy, status, logs, and resource commands
  • agents-pay:
    • v1 payment manager, connector, and credential provisioning
    • --no-auto-payment in operator-approved payment flows
    • OpenClaw and human-admin setup instructions
    • unambiguous manager and connector discovery in the bundled Python scripts
  • amazon-bedrock Harness migration guides, in both repository copies:
    • v1 Harness YAML and Gateway target configuration
    • migration mapping for action groups and knowledge bases
    • corrected local dev guidance and reference links

Version policy: Updated skills require CLI v1.0.0 or later and use the v1 project format ("version": 2). For v0 projects, they direct users to review an agentcore migrate plan before applying it

Type of Change

  • New plugin
  • New skill
  • Bug fix
  • Documentation update
  • CI/CD change
  • Other

Checklist

  • I have read the CONTRIBUTING guide
  • My changes pass python3 tools/validate.py
  • I have updated relevant documentation

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@nborges-aws
nborges-aws requested review from a team as code owners October 29, 2026 17:09
@nborges-aws nborges-aws changed the title Nickdb/agentcore cli v1 feat(aws-agents): update skills to reflect AgentCore CLI v1 Oct 29, 2026
payments = (target.get("resources") or {}).get("payments")
if not payments:
payments = data.get("payments")
if not payments:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use agentcore status first when this is a v1 project? Migration keeps the old deployed-state.json, but v1 no longer updates its payments branch. If a manager or connector is replaced after migration, this path keeps returning the old IDs without ever checking status.

I reproduced this with a version-2 project and stale payment entries: it returned the old connector and made zero status calls. The updated setup_payment_user.py already does status-first discovery. It would be worth adding a regression test for this migrated-project case here too.


## Add Gateway targets

An action-group shim is a new Lambda backed Gateway target. Render the source action group into `tools/<shim>/handler.py` using the templates in this skill's `assets/`, with one `toolDefinitions` entry per source function or OpenAPI operation. Store the complete target object in a JSON file and add it through the CLI:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we keep the instruction to create a pyproject.toml alongside each rendered shim? The empty project and Harness scaffold don't create one in tools/<shim>, and the v1 CDK Python packager still requires it.

Following this guide with just handler.py fails with MissingProjectFileError: Required project file not found: .../tools/action-group/pyproject.toml. I reproduced that with the published @aws/agentcore-cdk@1.0.0 package. A minimal manifest example would help here; the mirrored guide under skills/core-skills needs the same instruction.

@notgitika notgitika left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@notgitika
notgitika merged commit d369825 into gitika/agentcore-cli-v1 Oct 29, 2026
@notgitika
notgitika deleted the nickdb/agentcore-cli-v1 branch October 29, 2026 20:08
nborges-aws added a commit that referenced this pull request Nov 6, 2026
* feat(aws-agents): update skills to reflect AgentCore CLI v1

* fix(aws-agents): fix runtime and harness configuration guidance

* fix(aws-agents): correct header allowlist example

* fix(aws-agents): ensure agent deployment workflows persist selected target

* fix(aws-agents): fix Privy guidance in payments skill

* fix(aws-agents): persist selected target on gateway and policy operations

* fix(aws-agents): fix payment admin setup instructions

* fix(aws-agents): update agent auth and cross-session memory examples

* fix: address review findings for agentcore CLI v1 skill updates

* fix(aws-agents): require shim manifests and prefer v1 payment status
nborges-aws added a commit that referenced this pull request Nov 6, 2026
* feat(aws-agents): update skills to reflect AgentCore CLI v1

* fix(aws-agents): fix runtime and harness configuration guidance

* fix(aws-agents): correct header allowlist example

* fix(aws-agents): ensure agent deployment workflows persist selected target

* fix(aws-agents): fix Privy guidance in payments skill

* fix(aws-agents): persist selected target on gateway and policy operations

* fix(aws-agents): fix payment admin setup instructions

* fix(aws-agents): update agent auth and cross-session memory examples

* fix: address review findings for agentcore CLI v1 skill updates

* fix(aws-agents): require shim manifests and prefer v1 payment status
nborges-aws added a commit that referenced this pull request Nov 11, 2026
* feat(aws-agents): update skills to reflect AgentCore CLI v1

* fix(aws-agents): fix runtime and harness configuration guidance

* fix(aws-agents): correct header allowlist example

* fix(aws-agents): ensure agent deployment workflows persist selected target

* fix(aws-agents): fix Privy guidance in payments skill

* fix(aws-agents): persist selected target on gateway and policy operations

* fix(aws-agents): fix payment admin setup instructions

* fix(aws-agents): update agent auth and cross-session memory examples

* fix: address review findings for agentcore CLI v1 skill updates

* fix(aws-agents): require shim manifests and prefer v1 payment status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants